ci: update branch-pattern matching #3030
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In freifunk-gluon#2997 it was pointed out the current branch-trigger matches more branches than the release-branches. Retrict the match-pattern to only cover release-branches Also only trigger builds on the next-branch and not branches prefixed with this name. Link: freifunk-gluon#2997 (comment) Signed-off-by: David Bauer <[email protected]>
Add a workflow-dispatch trigger to the build-workflow to enable triggering build-tests on branches not covered from the match pattern. Signed-off-by: David Bauer <[email protected]>
neocturne
requested changes
Oct 19, 2023
It makes sense to run CI build-tests in case the CI itself is altered. Signed-off-by: David Bauer <[email protected]>
blocktrron
force-pushed
the
ci-restrictive-target-match
branch
from
ae75811
to
3bfea8e
Compare
neocturne
approved these changes
Oct 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
github: restrict branch-triggers on specific branches
In #2997 it was pointed out the current branch-trigger matches more
branches than the release-branches. Retrict the match-pattern to only
cover release-branches
Also only trigger builds on the next-branch and not branches prefixed
with this name.
Link: #2997 (comment)
github: add workflow-dispatch trigger for build workflow
Add a workflow-dispatch trigger to the build-workflow to enable
triggering build-tests on branches not covered from the match
pattern.
github: trigger ci-build when altering ci
It makes sense to run CI build-tests in case the CI itself is altered.